s are often completely useless in virtual machines. Kind regards, Sven
osed to using netplan as a "common interface" by default until it has better integration.Cheers,Sven
https://www.compmall.de/VDX3-EITX-75S-505669 is in stock.I found a variety of other shops selling similar boards, some having them in stock, some not.Am 08.06.2024 13:29 schrieb rhys :Yes, this is a known issue. This is because Bookworm only supports 32-bit CPUs that are fully Intel compatible. Y
d be explicitly ignored in lintian (and
> someone has probably filed a bug about that).
Yes, #1067040[1]. IIUC, the issue should be fixed in lintian git
already[2].
Cheers,
Sven
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067040
2.
https://salsa.debian.org/lintian/lintian/-/commit/07167eebb697d74d84627b275d8aeff4ebf32f7e
Am 23.05.2024 20:16 schrieb Bernd Zeimetz :On Thu, 2024-05-23 at 11:01 +0900, Simon Richter wrote:
> Yes, but unironically: experimental is a side branch, unstable is a
> MR,
> and testing is the main branch.
>
> It is entirely valid to be dissatisfied with the turnaround time of
> the
> e
ies automatic deleting at some point IMHO.Now, bad choices by various tools have been mentioned, so a cleaner for these directories that runs outside a reboot has to be careful anyhow. But during a reboot? I don't think that should be too much of a problem. Cheers, Sven
rect, as it woul be in English "renamed".
That is exactly what is used in the original:
$ LANG=C mv -v test2/bla.txt test1/
renamed 'test2/bla.txt' -> 'test1/bla.txt'
Cheers,
Sven
bootstrap script fetches files over the network, so it is
not possible to build the Debian package from upstream git tags. At the
very least it would lack any translations, and there is also the
problem of the gnulib submodule.
Cheers,
Sven
pkg-dev (>= 1.22.5) which would have prevented their
migration to testing. Testing users on armel and armhf should avoid
installing them and downgrade to the pre-t64 version if necessary.
Cheers,
Sven
On 2024-03-02 08:47 +0100, Sven Joachim wrote:
> On 2024-03-02 08:01 +0100, Andreas Metzler wrote:
>
>> iirc it was recently proposed to add a suggestion to run dpkg --verify
>> to the trixie upgrade notes to find missing files due to the usr-merge
>> transition. (Cannot
ibuuid1 needs to be reinstalled.
The libuuid1 package should do something to prevent that file loss,
e.g. declaring its own Replaces+Conflicts on libuuid1t64.
Cheers,
Sven
See
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025964
> https://salsa.debian.org/debian/ncurses/-/commit/11d067455801fddf8c65eba6e447ef7aacd1d703
>
> Using bookworm/stable to build AOSP is not an option?
It is also possible to install the bookworm libncurses5/libtinfo5
packages on newer releases. There are no dependencies besides libc6,
after all.
Cheers,
Sven
.
So if you install systemd units there, adding a build-dependency on
debhelper (>= 13.11.6~) is probably advisable, lest backports run into
#1041159[1].
Cheers,
Sven
1. https://bugs.debian.org/1041159
-debug 2.1.8-1 amd64
debug symbols for libopeniscsiusr
libopeniscsiusr-dev/stable,stable 2.1.8-1 all
I.e. they don't actually contain the word “penis”, they just happen to
contain words that when strung together contain these letters in this order.
Regards
Sven
en gets followed up by
> a MBF effort.
> As the FTBFS wrt libfreetype6-dev was predicted and announced [1], wouldn't it
> have been better if the MBF had taken place?
At the time I recommended just removing the libfreetype6-dev package[2],
based on my experience with the transi
Package: wnpp
Severity: wishlist
Owner: Sven Joachim
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: wtmpdb
Version : 0.8.0
Upstream Contact: Thorsten Kukuk
* URL : https://github.com/thkukuk/wtmpdb
* License : BSD 2-Clause
Programming Lang: C
aded
compressors produce different output, and dpkg 1.21.14 switched from
single-threaded to multi-threaded compression. The hello package was
uploaded to the archive before the dpkg 1.21.14 release.
The uploader can also change the compression level with the -z option,
after which you might not be able to reproduce their debian.tar.xz so
easily.
Cheers,
Sven
e built reliably from git/VCS - the old debian stuff is
> bust'. Better would be a new git-only dpkg format of some sort with a
> new set of expectations. But that's quite a big piece of work.
>
> Just to be clear I don't want any of that. I want the existing tooling
> and packaging to work the way policy says it should, at least until it
> is agreed that policy has to change.
You can want whatever you like, but wanting does not make anything
happen magically.
Cheers,
Sven
lly been skeptical it worked like a charm. See the
discussion in #1032708.
Cheers,
Sven
on the bugs which actually
matter for these distributions.
Thanks,
Sven
libncurses5 and
libncursesw5 packages now. If you have objections, please raise them.
Cheers,
Sven
1. https://bugzilla.redhat.com/show_bug.cgi?id=2129865
2. https://bugzilla.redhat.com/show_bug.cgi?id=2135400
3. https://bugzilla.redhat.com/show_bug.cgi?id=2144184
4. https://bugzilla.redhat.
ecommends to point to
>dhcpcd-base instead of isc-dhcp-client
If my above statements about debootstrap are correct, this will result
in no dhcp-client being installed at all by debootstrap unless the
override bug also requests bumping dhcpcd-base's priority from optional
to important.
Cheers,
Sven
On 2023-06-10 10:39 +0200, Helmut Grohne wrote:
> Hi Sven,
>
> On Sat, Jun 10, 2023 at 08:35:44AM +0200, Sven Joachim wrote:
>> > Unfortunately, any
>> > external package that still ships stuff in /bin breaks this. In effect,
>> > any addon repository
On 2023-06-10 08:35 +0200, Sven Joachim wrote:
> Am 10.06.2023 um 07:35 schrieb Helmut Grohne:
>
>> One of the approaches to making bootstrapping work was adding the
>> symlinks to some data.tar. That has been category 2 from my earlier
>> mail. We definitely cannot add /b
that still ships stuff in /bin breaks this. In effect,
> any addon repository or old package can break your system.
You lost me. We have converted /bin to a symlink already, have many
packages that ship files there and yet our systems do not break. Could
you please elaborate?
Cheers,
Sven
installations even further.
That would only add some burden for fresh installations to install
bookworm first, and upgrade later on. At that point I guess we could
start to talk about retro computing if it's still running on i386. :)
Sven
think about the plans for Y2038 anyway.
Sven
with the last
package that contained these as directories, instantly hosing your
installation. I am pretty sure the dpkg maintainer will not like this.
Cheers,
Sven
thers) - Porting to other
architectures
often requires a different (newer) compiler version, which might lead to
failures with -Werror.
Cheers,
Sven
;-fdebug-prefix-map==.", and you have the same
problem. If you disable that as well via
DEB_BUILD_MAINT_OPTIONS=reproducible=-fixfilepath,-fixdebugpath, the
-dbgsym packages will most likely end up unreproducible.
Cheers,
Sven
x27;t tell him this.
>
> So I'm saying that Debian needs a mechanism to have his computer tell
> him to do this.
>
> Maybe the next time he uses apt*, somehow the system should tell him...
Somehow, but how exactly? Good question that was brought up on
debian-devel[2], alas
ootstrapping for a VM or physical system, you likely want the ability to do some stuff during first boot and can easily skip doing anything, since you actively would need to hook up into the first boot semantics to use them. (ConditionFirstBoot).Kind regards,Sven
simplistic
resolver only ever looks at the first alternative in dependencies, and
so usrmerge gets installed anyway. See #768062, for instance.
Cheers,
Sven
--no-info \
> --no-discard-stderr ./debian/tmp/usr/bin/vdb_print
> [...]
Your debian/rules file looks incorrect to me, the
override_dh_install-arch target requires to generate the manpages with
help2man _before_ installing the libraries into
/debian/tmp/usr/lib/$(DEB_HOST_MULTIARCH), so setting LD_LIBRARY_PATH is
rather useless.
Cheers,
Sven
the packages in question.
>
> Right. I think it would be immensely useful to have an actual
> reproducer so one could study the issue more closely or at least a bug
> report, which describes the issue in more detail, like the exact
> circumstances when this can happen.
> So far this is merely theoretical, right?
> Or do we have a documented instance of this happening?
#953562 seems to be such an instance.
Cheers,
Sven
dated its
existance.
And now this is so baked in to everything that suddenly allowing it
would break many programs, without a doubt.
In the end, this tag is a more "cantfix" than a "wontfix", because you
basically can't, without creating a new OS.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
t with non-free firmware,
right now it seems to be impossible to find.
The official netinst image advertised on the homepage is for servers and
virtual machines only. How is an average user of Windows or even other
GNU/Linux distributions supposed to know that official Debian images do
not offer network access during installation on desktops and laptops?
Cheers,
Sven
on do not affect whether the library is seen as needed.
| This is similar to the rules for extraction of object files from
| archives. '--no-as-needed' restores the default behaviour.
`
So,
g++ -o linktest debian/tests/hw.cc $(pkg-config --cflags --libs libola)
is probably you want instead.
HTH,
Sven
ckage must not declare a "Pre-
| Depends", "Depends", "Recommends", "Build-Depends", "Build-Depends-
| Indep", or "Build-Depends-Arch" relationship on a non-*main* package
| unless that package is only listed as a non-default alternative for
| a package in *main*),
`
Cheers,
Sven
configuration and the initrd are generated on the end user machine.
By default Debian doesn't enroll a MOK, so I don't see how the end user
machine would sign the grub configuration and the initrd, as there is
simply no key available that would be accepted by the UEFI.
Regards
Sven
pgpk6dvOVIChn.pgp
Description: Digitale Signatur von OpenPGP
all
loaded files with (taking care that a malicious party
can't just use the grub console to disable signature checking),
* sign generated grub configurations with ,
* sign generated initrds with .
Maybe some or all of these things are already possible with current
tooling, so please
On Sun, Jul 05, 2020 at 06:17:47PM -0300, Henrique de Moraes Holschuh wrote:
Hi,
> It depends. Are the CLIs involved compatible?
Yes and no. :)
If you just rely on `mkfs.exfat /dev/sdX` yes, if you want to use some special
options they are not.
Sven
the same binary names. (I did not yet check
if they are flag by flag compatible or not)
Cheers,
Sven
Package: wnpp
Severity: wishlist
Owner: Sven Hoexter
* Package name: exfatprogs
Version : 1.0.3
Upstream Author : Namjae Jeon
Hyunchul Lee
* URL : https://github.com/exfatprogs/exfatprogs
* License : GPL-2
Programming Lang: C
stable might have occurred. My apologies if that’s the case.)
>
> Doesn't that mean that locales-all rather should Provide all the
> individual locales ?
The locales package also contains three small programs and the
/etc/locale.alias file, neither of which are provided by locales-all.
Cheers,
Sven
ithout-manpage sbin/mkfs.ext4
> W: e2fsprogs-udeb udeb: binary-without-manpage sbin/resize2fs
> W: e2fsprogs-udeb udeb: binary-without-manpage sbin/tune2fs
> N: 5 tags overridden (2 errors, 3 info)
>
> By *definition* udebs aren't supposed to have changelogs, copyright
> files, or man pages, right?
Right.
Cheers,
Sven
ly include vim-tiny and nano, whereas an absolutely minimal
system does not include an interactive editor at all. On those you have
to edit files with shell redirection and sed.
Cheers,
Sven
On 2020-03-02 20:24 +0100, Tomas Pospisek wrote:
> On 02.03.20 18:06, Sven Joachim wrote:
>> On 2020-03-02 17:20 +0100, Tomas Pospisek wrote:
>>
>>> I just got a mail from the BTS, that this spam mail [1] has closed the
>>> bug report. I can't spot why that
ening, interested and would do
> some handholding then please tell).
This issue has been discussed for at least 16 years[1], so don't hold
your breath.
Cheers,
Sven
1. https://lists.debian.org/debian-devel/2004/03/thrd2.html#00847
g #949395), and when that library
starts be installed under /usr/lib, this will trigger symbol lookup
errors and the like. See #896019 and #948318 for examples.
Cheers,
Sven
does actually work.
I'm yet sure if this question was more trolling then anything else.
Nobody should browse the internet with a browser from 2013 in 2019.
Sven
ory
are different from user to user (mostly depending on their umask), and
are propagated to the debian.tar.xz.
When building from a fresh clone, timestamps of files in the
debian.tar.xz should be set to the date of the latest debian/changelog
entry, as dpkg-source will clamp their mtimes to that value. But in an
existing git repository there will likely be files older than that, and
their random mtime also propagates to the debian.tar.xz.
Cheers,
Sven
, but container based service management (such as
kubernetes or docker swarm) are (at least in my experience) a lot easier
to manage and more effective, when you consistently separate each
service into its own container.
Regards
Sven
signature.asc
Description: OpenPGP digital signature
Package: wnpp
Severity: wishlist
Owner: Sven Hoexter
* Package name: jattach
Version : 1.5
Upstream Author : Andrei Pangin
* URL : https://github.com/apangin/jattach/releases
* License : Apache 2.0
Programming Lang: C
Description : JVM Dynamic Attach
Package: wnpp
Severity: wishlist
Owner: Sven Eckelmann
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: ap51-flash
Version : 2019.0
Upstream Author : Marek Lindner
* URL : https://github.com/ap51-flash/ap51-flash
* License : GPL-3+
Programming
ile over the
network may allow tracking your machine.
https://github.com/systemd/systemd/pull/4645
https://superuser.com/questions/1214704/can-an-attacker-exploit-my-etc-machine-id
HTH,
Sven
VMware cluster when an
iSCSI-backed LUN when down but you should be easily able to reproduce
this with a simple local KVM setup.
Grüße,
Sven.
signature.asc
Description: OpenPGP digital signature
tains the development files.
>
> But as near as I can tell, it's a real package:
>
> https://packages.debian.org/buster/libfuse3-dev
This can happen if you have assigned a negative Pin-Priority to
libfuse3-dev. According to apt_preferences(5), a Priority < 0 "prevents
the version from being installed", and apparently apt achieves this by
pretending that the package is not there at all.
Cheers,
Sven
Andrey Rahmatullin wrote:
> [-- text/plain, encoding quoted-printable, charset: utf-8, 11 lines --]
> On Fri, Apr 05, 2019 at 09:07:06PM +0200, Sven Hartge wrote:
>> CMake is a bit "special" in that regard. To get the right hardening
>> flags to work for some parts
Otto Kekäläinen wrote:
> I've read this section many times over but I don't get it. A
> workaround is presented but since we are on a new debhelper it is
> advised not to be used. It suggests using
> /usr/share/dpkg/buildflags.mk but since we already call default.mk the
> buildflags.mk should be
Bug #882993, updatedb.mlocate will never be run automatically if cron
and anacron are not installed.
Cheers,
Sven
Sven Hartge wrote:
> Sven Hartge wrote:
>> I changed the resolver to use a combination of mk-build-deps and
>> aptitude, the same as sbuild and pbuilder use to resolve build-deps, to
>> better handle alternatives.
>> You may have hid an edge case I didn't encoun
Sven Hartge wrote:
> I changed the resolver to use a combination of mk-build-deps and
> aptitude, the same as sbuild and pbuilder use to resolve build-deps, to
> better handle alternatives.
> You may have hid an edge case I didn't encounter during my testing.
Hmm, I may see th
dle alternatives.
You may have hid an edge case I didn't encounter during my testing.
> [1] https://salsa.debian.org/debian/nix/blob/kaiha/wip/debian/control
Do you have a pipeline log on Salsa showing the mis-selection of
build-deps? During a cursory glance I could only find logs showing t
18 Aug 31 16:02 aureport -> /usr/sbin/aureport
lrwxrwxrwx 1 root root18 Aug 31 16:02 ausearch -> /usr/sbin/ausearch
lrwxrwxrwx 1 root root17 Aug 31 16:02 autrace -> /usr/sbin/autrace
lrwxrwxrwx 1 root root19 Aug 31 16:00 badblocks -> /usr/sbin/badblocks
lrwxrwxrwx 1 root root15 Nov 30 09:03 blkid -> /usr/sbin/blkid
[...]
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
, this does not happen.
The "Custom CI config path" setting does not influence this.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
"bumblebee-nvidia depends on nvidia-driver | ... " but downgraded this
> dependency to "RECOMMENDED but will NOT be installed". That is really strange
> since aptitude seems to have ignored a hard dependency.
It didn't, it just chose to install nvidia-kernel-dkms rather than
nvidia-legacy-340xx-driver. The installation of various 386 packages is
certainly odd and probably not what you want, but I am pretty sure that
aptitude's solution is valid, if suboptimal.
The xserver-xorg-video-nvidia package recommends nvidia-driver, so the
"RECOMMENDED but will NOT be installed" statement is also explained.
Cheers,
Sven
890890.
Cheers,
Sven
On 2018-02-21 19:36 +0100, Tobias Frost wrote:
> On Wed, Feb 21, 2018 at 06:31:46PM +0100, Sven Joachim wrote:
>> On 2018-02-21 17:48 +0100, Georg Faerber wrote:
>>
>
>> Apart from restricting access to the BTS (which I think nobody really
>> wants), the answer is
long, those
messages should be quite easy to filter out.
Cheers,
Sven
ng
> or it is planned to disable it also?
There was already a longer discussion about the future of those lists,
which originated at
https://lists.debian.org/debian-devel-announce/2017/09/msg4.html
But so far no outcome as far as I followed the discussion.
Cheers,
Sven
red
>> people jumping through hoops while PragBF just works.
> Could you link to PragBF? I can't find any mention of it on web search
> engines.
ROT13: CentOS
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
The Wanderer wrote:
> On 2017-12-01 at 16:44, Sven Hartge wrote:
>> Luca Capello wrote:
>>> On Fri, 01 Dec 2017 14:59:53 -0500, James McCoy wrote:
>>>> People seem to be skipping over the fact that even after ntfs-3g
>>>> was installed, the u
Luca Capello wrote:
> On Fri, 01 Dec 2017 14:59:53 -0500, James McCoy wrote:
>> People seem to be skipping over the fact that even after ntfs-3g was
>> installed, the user only had RO access. That's the bigger issue.
> Exactly, which IIRC is the normal behavior if the NTFS filesystem was
> not
wer CPU families
> mostly keep their GNU CPU and Linux uname -m identical, so maybe only
> the historically weird ones (i386, arm*, p(ower)pc, mips(64)el) would
> need special cases?
Using uname -m seems to be wrong, since there are many 32-bit
architectures where the kernel can be 64-bit.
Cheers,
Sven
radius-users/2017-August/088521.html
It would be really interesting to gather some long term statistics about
this to see a trend of the adoption of newer TLS versions over time.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
ion usable for any real world application.
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Kurt Roeckx wrote:
> On Fri, Aug 11, 2017 at 01:34:53PM +0200, Sven Hartge wrote:
>> Marco d'Itri wrote:
>>> On Aug 09, Sven Hartge wrote:
>> >> Looking at https://developer.android.com/about/dashboards/index.html
>> >> there is still a mark
n the application to only use TLS1.2 (unless changed by the
administrator).
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
Marco d'Itri wrote:
> On Aug 09, Sven Hartge wrote:
>> Looking at https://developer.android.com/about/dashboards/index.html
>> there is still a marketshare of ~25% of smartphones based on Android
>> 5.0 and 5.1 and 16% based on 4.4. So this change would (at the
>&g
d on Android 5.0
and 5.1 and 16% based on 4.4. So this change would (at the moment) block
~40% of Android smartphones from connecting to any WLAN using PEAP or
TTLS.
And when I look at other wireless-enabled things, the ratio for support
for TLS1.2-only might be even worse and less quick to change.
y be to leave the conffile alone, at least until
dpkg itself is able to take care of the problem[2].
Cheers,
Sven
1. https://wiki.debian.org/DpkgConffileHandling
2. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=822462
id in the past.
Maybe my viewpoint is a bit limited because I only use chromium when I've
to rely on some Chrome extensions and otherwise use Firefox. So I was
confused when I noticed this behaviour change and it took a a few minutes
and some grief to figure what had changed
Sven
On 2017-01-27 20:16 -0800, Thomas Nyberg wrote:
> On 01/25/2017 11:18 PM, Sven Joachim wrote:
>> This seems to be a recurring problem in Mozilla's build process, it
>> fails because SHELL is not set in the environment. You can work around
>> that by passing --preser
recurring problem in Mozilla's build process, it
fails because SHELL is not set in the environment. You can work around
that by passing --preserve-envvar=SHELL to debuild.
Related links:
https://lists.alioth.debian.org/pipermail/pkg-mozilla-maintainers/2016-January/027040.html
https://bugzilla.mozilla.org/show_bug.cgi?id=1213959
Cheers,
Sven
tretch because they depend on the virtual package libtk
> which is provided by libtk8.4, libtk8.5 and libtk8.6, and likely only
> the first dependency
> in lexicographic order is checked.
>
> Should I report a bug? Where?
No need to do so, this has been filed[1] quite some time ago already.
Cheers,
Sven
1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=745475
is the best way to do this?
>
> Depend on dpkg-dev and use dpkg-architecture?
Please not.
> dpkg-architecture -q DEB_HOST_MULTIARCH
>
> I don't know of a better way.
Resolve $DEB_HOST_MULTIARCH at build time[1], when dpkg-architecture is
known to be around.
Cheers,
c/skel/.profile', does not exist on system.
| Installing new config file as you requested.
| [...]
| # ls -l /etc/skel/.profile
| -rw-r--r-- 1 root root 675 Nov 15 18:49 /etc/skel/.profile
`
IIRC --force-confmiss has always installed missing conffiles without
asking, and it's much older than --force-confask.
Cheers,
Sven
at least 12 years[1].
Cheers,
Sven
1. https://lists.debian.org/debian-security/2004/09/msg00014.html
nge the date in the binNMU entry, SOURCE_DATE_EPOCH should
> probably be set to the date of the last sourceful upload (instead of
> just using the most recent changelog entry).
Wouldn't this cause dpkg-deb to clamp the mtime to that date, precisely
the problem this thread is all about?
Cheers,
Sven
intainer script
> manually.
In dpkg versions before 1.16.1 those bad maintainer scripts would
actually fail to run, but as a consequence of the fix for bug #622094[1]
dpkg is more tolerant now. Unfortunately this has caused quite a few of
these broken scripts to creep into the distribution.
Cheers,
Sven
1. https://bugs.debian.org/622094
, severity=serious would be in order, right?
Maybe, but I don't think it's worth to fix such bugs in stable. Since
dpkg calls maintainer scripts via execvp(3), the missing shebang does
not really have bad consequences as they end up being run by /bin/sh
anyway.
Cheers,
Sven
- - -=-=-=-=-=- Don't Delete Anything Between These Lines =-=-=-=-=-=-=-=-
d495b767-7754-4e61-80ea-8b31c07f3595
[ 2 ] Choice 1: Repeal previous GR
[ 1 ] Choice 2: Acknowledge difficulty
[ 4 ] Choice 3: Remain private
[ 3 ] Choice 4: Further Discussion
- - -=-=-=-=-=- Don't Delete Anything Between T
_ a highly Linux-centric package, so catering
for Hurd or FreeBSD does not apply here, but still ...
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
f course not. Like many other subjects on debian-devel, this one has
been discussed extensively more than ten years ago[1,2].
Cheers,
Sven
1. https://lists.debian.org/debian-devel/2004/03/msg00847.html
2. https://lists.debian.org/debian-devel/2005/07/msg01106.html
On Wed, 27 Jul 2016 23:09:36 +0200
Tollef Fog Heen wrote:
> ]] Sven Bartscher
>
> > I am a developer and regardless of the distribution I use, I often have
> > a slow internet connection. So having to download possibly large
> > documentation is a problem for me.
g up-to-date (like
> testing or unstable) and so therefore are more likely to be able to
> handle the bandwidth cost.
I am a developer and regardless of the distribution I use, I often have
a slow internet connection. So having to download possibly large
documentation is a problem for me.
Regards
Sven
; 9791.99951171875 -> offset by 2 sectors to the front
sda5 -> 40108032/4096 -> 9792 (aligned correctly)
Grüße,
Sven.
--
Sigmentation fault. Core dumped.
;>packages.
>>
>> * Proposed deadline: June 1st 2016
>>- Assuming 14 days to review this mass bug filing, we would file the
>> bugs on the 18th of April. This would leave a bit over a month for
>> packages to be fixed.
>
> Thi
ial package, the same way it could ensure
that NSS or PAM modules are pulled in for every enabled architecture.
Cheers,
Sven
1 - 100 of 893 matches
Mail list logo
