Bug#1023517: openconnect: SSO with anyconnect V2 fails
Package: openconnect Version: 9.01-1 Severity: normal Dear Maintainer, due to missing patch https://gitlab.com/openconnect/openconnect/-/commit/0e82c9371420db42376f7952f0d756222aba1001, SSO with anyconnect V2 fail. I tested the patch from the commit above and it works for me. The bug was also reported to ubuntu: https://bugs.launchpad.net/ubuntu/+source/openconnect/+bug/1993901 Best wishes, Marc -- System Information: Debian Release: bookworm/sid APT prefers kinetic-updates APT policy: (500, 'kinetic-updates'), (500, 'kinetic-security'), (500, 'kinetic-proposed'), (500, 'kinetic') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.19.0-23-generic (SMP w/8 CPU threads; PREEMPT) Kernel taint flags: TAINT_OOT_MODULE Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages openconnect depends on: ii libc62.36-0ubuntu4 ii libgnutls30 3.7.7-2ubuntu2 ii libopenconnect5 9.01-1 ii libproxy1v5 0.4.18-1 ii libxml2 2.9.14+dfsg-1 ii vpnc-scripts 0.1~git20220510-1 Versions of packages openconnect recommends: ii python3 3.10.6-1 ii python3-asn1crypto 1.5.1-1 ii python3-mechanize 1:0.4.8+pypi-4 ii python3-netifaces 0.11.0-1build2 Versions of packages openconnect suggests: ii bash-completion 1:2.11-6ubuntu1 -- no debconf information
Bug#979324: tegrarcm/1.8-2 [RC] -- Tool to upload payloads in Tegra SoC recovery mode
Package: sponsorship-requests Severity: important Dear mentors, I am looking for a sponsor for my package "tegrarcm": * Package name: tegrarcm Version : 1.8-2 Upstream Author : [fill in name and email of upstream] * URL : https://github.com/NVIDIA/tegrarcm * License : proprietary, BSD-3-clause * Vcs : [fill in URL of packaging vcs] Section : non-free/utils It builds those binary packages: tegrarcm - Tool to upload payloads in Tegra SoC recovery mode To access further information about this package, please visit the following URL: https://mentors.debian.net/package/tegrarcm/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/non-free/t/tegrarcm/tegrarcm_1.8-2.dsc Changes since the last upload: tegrarcm (1.8-2) unstable; urgency=medium . * Update to Debian Standards version 4.5.1 * Re-Upload (Closes: #978478) Regards, -- Marc Dietrich
Bug#905569: RFS: cbootimage/1.7-1+b1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "cbootimage": * Package name: cbootimage Version : 1.7-1+b1 Upstream Author : Jimm Zhang * URL : https://github.com/NVIDIA/cbootimage * License : GPL-2 Section : utils It builds those binary packages: cbootimage - Tools to dump and generate boot config table on Tegra devices To access further information about this package, please visit the following URL: https://mentors.debian.net/package/cbootimage Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/c/cbootimage/cbootimage_1.8-1.dsc More information about tegrarcm can be obtained from https://github.com/NVIDIA/cbootimage Changes since the last upload: * new upstream release Regards, Marc Dietrich
Bug#905567: RFS: tegrarcm/1.7-1
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "tegrarcm": * Package name: tegrarcm Version : 1.7-1 Upstream Author : Allen Martin * URL : https://github.com/NVIDIA/tegrarcm * License : BSD-3 clause / proprietary Section : utils It builds those binary packages: tegrarcm - Tool to upload payloads in Tegra SoC recovery mode To access further information about this package, please visit the following URL: https://mentors.debian.net/package/tegrarcm Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/non-free/t/tegrarcm/tegrarcm_1.8-1.dsc More information about tegrarcm can be obtained from https://github.com/NVIDIA/tegrarcm Changes since the last upload: * new upstream release Regards, Marc Dietrich
Bug#828009: Typo in package description
Am Donnerstag, 23. Juni 2016, 11:29:40 CEST schrieben Sie: > Package: cbootimage > Version: 1.4-1 > Severity: minor > > | bootloader (e.g. u-boot) read to be flashed to a storage device. > > read -> ready ? yes. Does this require a re-submisson? Marc signature.asc Description: This is a digitally signed message part.
Bug#827071: New upstream release
New release uploaded to mentors.debian.net. I'm not a DD, so this (tegrarcm) and cbootimage (also on mentros.debian.net) are looking for a sponsor.
Bug#760505: ITP: cbootimage-configs -- cbootimage configuration files for various NVIDIA Tegra boards
package: wnpp Severity: wishlist Owner: 'Marc Dietrich' *Package Name : cbootimage-configs Version : 0.0+20140806~git18e531f-1 Upstream Author : Stephen Warren *URL : https://github.com/NVIDIA/cbootimage-configs *License : ZLIB *Description : cbootimage configuration files for various NVIDIA Tegra boards This package includes configuration files for cbootimage. They are mainly provided for reference. The user needs to copy them to his home directory and call an included script which compiles some data tables and adds the bootloader afterwards. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741648: RFS: cbootimage/1.2-2
Am Montag 25 August 2014, 14:35:40 schrieb Eriberto:
> Hi Marc,
>
> 2014-08-25 10:47 GMT-03:00 Marc Dietrich :
> >> 1. d/control:
> >> - Change debhelper from 9.0.0 to 9.
>
> You didn't it.
ups, I thought you meant the compat file.
>
> >> - Create a VCS to control your /debian versions. You can use
> >>
> >> github or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to
> >> d/control.
> >
> > mmh, dpkg-buildpackage seems not to understand Vcs-* tags (Ubuntu 14.04).
> > I added them anyways.
>
> I think you didn't undertand my words. You must create a VCS to
> control your packaging (debian directory). Not create a VCS to point
> to upstream code. The Vcs-Git field must use git:// instead https://.
> Your mistake was put the Vcs-* in binaries instead in source block
> (after Homepage field).
This and the problems below are a result of how I package the source. Let me
explain it at bit more: cbootimage is used to flash the bootloader on tegra
devices. To do this, it needs some machine specific config files. These config
files are not part of the cbootimage repository, instead they live under their
own one. To avoid creating two source packages, I decided to include the
config tree in the program tree. This is possible according to
https://wiki.debian.org/Projects/DebSrc3.0 (How to use multiple upstream
tarball in 3.0 (quilt) format?). So I have two tarballs now:
cbootimage_1.4.orig.tar.gz and
cbootimage_1.4.orig-configs.tar.gz
which create a binary and an platform independend package. So both packages
need their own copyright (before cbootimage-1.0 didn't contain the config
files).
I wonder if I should just add a plain "copyright" file which only contains my
stuff under debian/*.
Regarding Vcs fields, I haven't found a solution how to add multiple Vcs-*
fields (for multiple source tarballs). At least the debian handbook allows it.
Github defaults to https btw.
>
> >> 2. d/copyright: update the packaging copyright years from 2013 to
> >> 2013-2014 and upstream copyright years to 2012-2013.
> >
> > ok.
>
> Your packaging years are wrong. You already have the cbootimage 1.0-1
> in Debian and it was uploaded in 2013. You renamed the d/copyright to
> d/cbootimage.copyright. This procedure is inadequate.
>
> >> 3. Do you saw that already there the 1.4 version?
> >
> > yes, I already created a 1.3 version. Nevertheless, I updated to 1.4 now.
>
> Ok.
>
> >> 4. Some lintan messages[2] that you need to fix:
> >>
> >> cbootimage: description-possibly-contains-homepage
> >> http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html.
> >>
> >> W: cbootimage: binary-without-manpage usr/bin/bct_dump
> >> W: cbootimage: binary-without-manpage usr/bin/cbootimage
> >
> > In v1.3 I added man (self written) pages. I still want to convert them
> > using a more common tool (from xml to man). Maybe later.
> >
> > I also added the config files for cbootimage, which normally live in a
> > seperate repository. I didn't want to create another source package for
> > these, because basicly, they belong together (you cannot use cbootimage
> > without a config, but you can run it).
>
> Sorry but not acceptable. You can't 'inject' code in original upstream
> code. Debian will distribute this source code as original. So, you
> must keep it original.
see above.
>
> > Feel free to re-check the result.
>
> You have several Lintian messages:
>
> I: cbootimage source: quilt-patch-missing-description add-man-pages.diff
> W: cbootimage source: no-debian-copyright
> P: cbootimage source: debian-watch-may-check-gpg-signature
> P: cbootimage-configs: no-upstream-changelog
> E: cbootimage-configs: copyright-should-refer-to-common-license-file-for-gpl
> I: cbootimage-configs: extended-description-is-probably-too-short
> W: cbootimage-configs: package-contains-vcs-control-file
> usr/share/cbootimage/configs/.gitignore
> W: cbootimage-configs: executable-not-elf-or-script
> usr/share/cbootimage/configs/tegra124/nvidia/jetson-tk1/PM375_Hynix_2GB_H5TC
> 4G63AFR_RDA_924MHz.bct.cfg W: cbootimage-configs:
> executable-not-elf-or-script
> usr/share/cbootimage/configs/tegra30/toradex/colibri_t30/colibri_t30_12MHz_1
> GB_NT5CC256M16CP-DI_400MHz-shmoo.bct.cfg P: cbootimage:
> no-upstream-changelog
mmh, I'm about to install a jessie system in a vm to get a current lintian. I
guess I can ignore the pedantic warnings for now?
How to fix the wrong permissions?
Rest should be fixed now.
> Your package needs more attention if you really want to upload it to
> Debian. Please, read the 'Debian New Maintainers Guide'[1] to you
> understand how a Debian package works.
well, I read this. I'm not packaging stuff on a daily basis (maybe only one
per year?), and have only limited time. So forgive me if my respond is slow
and issues still exist.
Marc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741648: RFS: cbootimage/1.2-2
tags 741648 - moreinfo
thanks
Hi Eriberto,
Am Dienstag 19 August 2014, 10:20:45 schrieb Eriberto Mota:
> Hi Marc,
>
> Please:
>
> 1. d/control:
> - Consider change the priority to optional. Please, read it[1].
> - Change debhelper from 9.0.0 to 9.
> - Create a VCS to control your /debian versions. You can use
> github or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to
> d/control.
mmh, dpkg-buildpackage seems not to understand Vcs-* tags (Ubuntu 14.04).
I added them anyways.
> 2. d/copyright: update the packaging copyright years from 2013 to
> 2013-2014 and upstream copyright years to 2012-2013.
ok.
> 3. Do you saw that already there the 1.4 version?
yes, I already created a 1.3 version. Nevertheless, I updated to 1.4 now.
>
> 4. Some lintan messages[2] that you need to fix:
>
> cbootimage: description-possibly-contains-homepage
> http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html.
>
> W: cbootimage: binary-without-manpage usr/bin/bct_dump
> W: cbootimage: binary-without-manpage usr/bin/cbootimage
In v1.3 I added man (self written) pages. I still want to convert them using
a more common tool (from xml to man). Maybe later.
I also added the config files for cbootimage, which normally live in a
seperate repository. I didn't want to create another source package for these,
because basicly, they belong together (you cannot use cbootimage without a
config, but you can run it).
Feel free to re-check the result.
Marc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741648: RFS: cbootimage/1.2-2
Hi Eriberto,
Am Dienstag 19 August 2014, 10:20:45 schrieb Eriberto Mota:
> Hi Marc,
>
> Please:
>
> 1. d/control:
> - Consider change the priority to optional. Please, read it[1].
> - Change debhelper from 9.0.0 to 9.
> - Create a VCS to control your /debian versions. You can use
> github or other. So, add the Vcs-Browser and Vcs-{Git|Svn|Cvs} to
> d/control.
mmh, dpkg-buildpackage seems not to understand Vcs-* tags (Ubuntu 14.04).
I added them anyways.
> 2. d/copyright: update the packaging copyright years from 2013 to
> 2013-2014 and upstream copyright years to 2012-2013.
ok.
> 3. Do you saw that already there the 1.4 version?
yes, I already created a 1.3 version. Nevertheless, I updated to 1.4 now.
>
> 4. Some lintan messages[2] that you need to fix:
>
> cbootimage: description-possibly-contains-homepage
> http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html.
>
> W: cbootimage: binary-without-manpage usr/bin/bct_dump
> W: cbootimage: binary-without-manpage usr/bin/cbootimage
In v1.3 I added man (self written) pages. I still want to convert them using
a more common tool (from xml to man). Maybe later.
I also added the config files for cbootimage, which normally live in a
seperate repository. I didn't want to create another source package for these,
because basicly, they belong together (you cannot use cbootimage without a
config, but you can run it).
Feel free to re-check the result.
Marc
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741649: RFS: tegrarcm/1.5-2
Hi Alex, Am Mittwoch, 21. Mai 2014, 15:56:46 schrieb Axel Beckert: > Marc Dietrich wrote: > > > Since in the meanwhile 1.6 is out, it would be nice if you could > > > incorporate the new upstream release into you next upload to mentors, > > > merging in the changelog entries from 1.5-1 and 1.5-2 into the one for > > > 1.6-1. > > > > ok, I updated it to 1.6. > > Thanks. Will have a look later when I'm back from work. > > > I also updated cbootimage to v1.3 following your comments above. It > > would be great if you could also sponsor this upload. > > Didn't know that package yet. Will have a look, too. bug 741648. I guess it needs some man page an a compile fix for kfreebsd. Thanks Marc signature.asc Description: This is a digitally signed message part.
Bug#741649: RFS: tegrarcm/1.5-2
Hi Alex, Am Sonntag, 18. Mai 2014, 18:45:54 schrieb Axel Beckert: > Hi Marc, > > Marc Dietrich wrote: > > I am looking for a sponsor for my package "tegrarcm" > > I'd generally sponsor that package as I'm one of its users (due to > owning a Toshiba AC 100. > > > * Package name: tegrarcm > > > >Version : 1.5-2 > > [...] > > > Changes since the last upload: > > > > tegrarcm (1.5-2) unstable; urgency=low > > > > * Add watch file > > * Update to Debian Standards version 3.9.5 > > > > tegrarcm (1.5-1) unstable; urgency=low > > > > * New upstream release > > There is only 1.2-2 in Debian, so the first upload of tegrarcm 1.5 to > Debian should be named 1.5-1, not 1.5-2. Consecutive uploads to > mentors do not need (and should not) bump the Debian release version. ok. > The package looks otherwise fine for me with one exception: To sponsor > it, I'd like to have to following lintian warning fixed: > > P: tegrarcm: no-homepage-field > > Please add a Homepage header to the source stanza of debian/control. > https://github.com/NVIDIA/tegrarcm looks like a reasonable value for > the Homepage field. done. > Since in the meanwhile 1.6 is out, it would be nice if you could > incorporate the new upstream release into you next upload to mentors, > merging in the changelog entries from 1.5-1 and 1.5-2 into the one for > 1.6-1. ok, I updated it to 1.6. I also updated cbootimage to v1.3 following your comments above. It would be great if you could also sponsor this upload. Thanks for help! Marc signature.asc Description: This is a digitally signed message part.
Bug#741649: RFS: tegrarcm/1.5-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "tegrarcm" * Package name: tegrarcm Version : 1.5-2 Upstream Author : a.mar...@nvidia.com from NVIDIA * URL : http://github.com/NVIDIA/tegrarcm * License : BSD / proprietary Section : utils It builds those binary packages: tegrarcm - Tool to upload payloads in Tegra SoC recovery mode To access further information about this package, please visit the following URL: http://mentors.debian.net/package/tegrarcm Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/non-free/t/tegrarcm/tegrarcm_1.5-2.dsc More information about hello can be obtained from http://http.download.nvidia.com/tegra-public-appnotes/flashing-tools.html Changes since the last upload: tegrarcm (1.5-2) unstable; urgency=low * Add watch file * Update to Debian Standards version 3.9.5 tegrarcm (1.5-1) unstable; urgency=low * New upstream release Regards, Marc Dietrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#741648: RFS: cbootimage/1.2-2
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "cbootimage" * Package name: cbootimage Version : 1.2-2 Upstream Author : Stephan Warren (swar...@nvidia.com) from NVIDIA * URL : http://github.com/NVIDIA/cbootimage * License : GPL 2+ Section : utils It builds those binary packages: cbootimage - Tools to dump and generate boot config table on Tegra devices To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cbootimage Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cbootimage/cbootimage_1.2-2.dsc More information about hello can be obtained from http://http.download.nvidia.com/tegra-public-appnotes/bct-overview.html. Changes since the last upload: cbootimage (1.2-2) unstable; urgency=low * Use Debian standards version 3.9.5 * Add watch file cbootimage (1.2-1) unstable; urgency=low * New upstream release Regards, Marc Dietrich -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#413985: ITP: elfio -- library for reading and generating ELF files
hi, why not getting rid of it as fedora does? As far as I know, it is only used for debugging purposes. The main secondlife-client main binary does not depend on it. marc Am Thursday 08 March 2007 14:08 schrieb Paul TBBle Hampson: > Package: wnpp > Severity: wishlist > Owner: "Paul "TBBle" Hampson" <[EMAIL PROTECTED]> > > * Package name: elfio > Version : 1.0.3 > Upstream Author : Serge Lamikhov-Center <[EMAIL PROTECTED]> > * URL : http://elfio.sourceforge.net/ > * License : LGPL > Programming Lang: C++ > Description : library for reading and generating ELF files > > elfio is a library for reading and generating ELF files > > Thoughts on the long description appreciated... Upstream has something > like: > elfio is a library for manipulating ELF files, which is > written in ANSI C++ and usable on a wide variety of > architectures > -- "The other side is solely responsible for the war." Lord Arthur Ponsonby, "Falsehood in Wartime: Propaganda Lies of the First World War", 1928 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
